Conversation
🦋 Changeset detectedLatest commit: cdc1abf The changes in this PR will be included in the next version bump. This PR includes changesets to release 13 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
WalkthroughThe pull request fixes an issue where the Biome language server fails to honour the Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
No actionable comments were generated in the recent review. 🎉 Comment |
| ConfigurationPathHint::FromLsp(path) | ConfigurationPathHint::FromWorkspace(path) => { | ||
| path.to_path_buf() | ||
| } | ||
| ConfigurationPathHint::FromUser(path) => { |
There was a problem hiding this comment.
I'm running into a similar issue as #9217, except with absolute paths. With some AI help and some local logs I narrowed the issue to this line. I basically have a biome.jsonc file in something like c:/code/configs/biome.jsonc and projects in c:/code/foo_project.
Before this PR, setting configurationPath in VSCode would fall back to the _ case below, which would use base_path() as path which is later used to open the project. IIUC, base_path would be the workspace's path.
After this PR, this branch runs which uses the parent of the configuration file which in my case is c:/code/configs/.
I added a log after this function and I see the following, which confirms the above.
[CUSTOM-BUILD] Registering project at path: "c:/code/configs"
I also added a log to text_document.rs in did_open() in session.project_for_path(). So when I try to format a file I see the following in the logs:
[CUSTOM-BUILD] Could not find project for c:/code/foo_project/bad_formatted.ts
I have a mostly AI written PR at b27112a but I need to clean it up. Feel free to take over it though!
Summary
Closes #7138
There were two bugs:
text_documentevent. Literally, we weren't checking forconfiguration_path.ProjectshashmapTest Plan
Heavy manual testing using the user's reproduction
Docs
N/A bug fix